Autogenerated HTML docs for v1.7.11-3-g60475 
diff --git a/gitnamespaces.html b/gitnamespaces.html index 18c11ce..02110d6 100644 --- a/gitnamespaces.html +++ b/gitnamespaces.html 
@@ -594,7 +594,7 @@  namespaces, each of which has its own branches, tags, and HEAD. Git can   expose each namespace as an independent repository to pull from and push   to, while sharing the object store, and exposing all the refs to  -operations such as .</p></div>  +operations such as <a href="git-gc.html">git-gc(1)</a>.</p></div>   <div class="paragraph"><p>Storing multiple repositories as namespaces of a single repository   avoids storing duplicate copies of the same objects, such as when   storing multiple branches of the same source. The alternates mechanism  @@ -606,7 +606,7 @@  refs in a directory under <tt>refs/namespaces/</tt>. For example,   <tt>GIT_NAMESPACE=foo</tt> will store refs under <tt>refs/namespaces/foo/</tt>. You   can also specify namespaces via the <tt>--namespace</tt> option to  -.</p></div>  +<a href="git.html">git(1)</a>.</p></div>   <div class="paragraph"><p>Note that namespaces which include a <tt>/</tt> will expand to a hierarchy of   namespaces; for example, <tt>GIT_NAMESPACE=foo/bar</tt> will store refs under   <tt>refs/namespaces/foo/refs/namespaces/bar/</tt>. This makes paths in  @@ -616,15 +616,15 @@  also avoids ambiguity with strange namespace paths such as <tt>foo/refs/heads/</tt>,   which could otherwise generate directory/file conflicts within the <tt>refs</tt>   directory.</p></div>  -<div class="paragraph"><p> and rewrite the  +<div class="paragraph"><p><a href="git-upload-pack.html">git-upload-pack(1)</a> and <a href="git-receive-pack.html">git-receive-pack(1)</a> rewrite the   names of refs as specified by <tt>GIT_NAMESPACE</tt>. git-upload-pack and   git-receive-pack will ignore all references outside the specified   namespace.</p></div>  -<div class="paragraph"><p>The smart HTTP server, , will pass  +<div class="paragraph"><p>The smart HTTP server, <a href="git-http-backend.html">git-http-backend(1)</a>, will pass   GIT_NAMESPACE through to the backend programs; see  - for sample configuration to expose  +<a href="git-http-backend.html">git-http-backend(1)</a> for sample configuration to expose   repository namespaces as repositories.</p></div>  -<div class="paragraph"><p>For a simple local test, you can use :</p></div>  +<div class="paragraph"><p>For a simple local test, you can use <a href="git-remote-ext.html">git-remote-ext(1)</a>:</p></div>   <div class="listingblock">   <div class="content">   <pre><tt>git clone ext::'git --namespace=foo %s /tmp/prefixed.git'</tt></pre>